SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 68112: A SAS® object spawner might stop accepting connections after several days of running

DetailsHotfixAboutRate It

In a grid environment starting with the SAS® 9.4M6 (TS1M6) maintenance release, an object spawner can stop accepting new connections and then generate an access violation error after several days of running.

During the incident there might be a build-up of open ports from SAS clients because connections are not freed. If the problem is not discovered, the number of open ephemeral ports can grow into the thousands.

Restarting the object spawner clears the error, and the system returns to a functioning state. Any open ports that were not freed during the incident are released.

The object spawner log might contain a traceback display similar to the following examples:

/sashome/SASFoundation/9.4/sasexe/tkepdl.so(tktracex+0x2e) [0x7f2dc89a97de]
/sashome/SASFoundation/9.4/sasexe/tkepdl.so(+0x54f2) [0x7f2dc89854f2]
/sashome/SASFoundation/9.4/sasexe/tkmk.so(bktExcept+0x62) [0x7f2dcfe12472]
/sashome/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7f2dcfe12ac4]
/lib64/libpthread.so.0(+0xf630) [0x7f2dd1225630]
/sashome/SASFoundation/9.4/sasexe/tkiomsvc.so(tktracex+0x2e) [0x7f16eef0809e]
/sashome/SASFoundation/9.4/sasexe/tkiomsvc.so(+0xd949) [0x7f16eee8c949]
/sashome/SASFoundation/9.4/sasexe/tkmk.so(bktExcept+0x62) [0x7f16fb418472]
/sashome/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7f16fb418ac4]
/lib64/libpthread.so.0(+0xf630) [0x7f16fc82b630]

This problem might occur between 5 and 8 days after the object spawner is first started.

A workaround is to restart the object spawner on a regular basis daily.

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Object Spawnerz/OS9.4_M69.4_M89.4 TS1M69.4 TS1M8
Microsoft® Windows® for x649.4_M69.4_M89.4 TS1M69.4 TS1M8
Microsoft Windows 8 Enterprise 32-bit9.4_M69.4_M89.4 TS1M69.4 TS1M8
Microsoft Windows 8 Enterprise x649.4_M69.4_M89.4 TS1M69.4 TS1M8
Microsoft Windows 8 Pro 32-bit9.4_M69.4_M89.4 TS1M69.4 TS1M8
Microsoft Windows 8 Pro x649.4_M69.4_M89.4 TS1M69.4 TS1M8
Microsoft Windows 8.1 Enterprise 32-bit9.4_M69.4_M89.4 TS1M69.4 TS1M8
Microsoft Windows 8.1 Enterprise x649.4_M69.4_M89.4 TS1M69.4 TS1M8
Microsoft Windows 8.1 Pro 32-bit9.4_M69.4_M89.4 TS1M69.4 TS1M8
Microsoft Windows 8.1 Pro x649.4_M69.4_M89.4 TS1M69.4 TS1M8
Microsoft Windows 109.4_M69.4_M89.4 TS1M69.4 TS1M8
Microsoft Windows Server 20089.4_M69.4_M89.4 TS1M69.4 TS1M8
Microsoft Windows Server 2008 R29.4_M69.4_M89.4 TS1M69.4 TS1M8
Microsoft Windows Server 2008 for x649.4_M69.4_M89.4 TS1M69.4 TS1M8
Microsoft Windows Server 2012 Datacenter9.4_M69.4_M89.4 TS1M69.4 TS1M8
Microsoft Windows Server 2012 R2 Datacenter9.4_M69.4_M89.4 TS1M69.4 TS1M8
Microsoft Windows Server 2012 R2 Std9.4_M69.4_M89.4 TS1M69.4 TS1M8
Microsoft Windows Server 2012 Std9.4_M69.4_M89.4 TS1M69.4 TS1M8
Microsoft Windows Server 20169.4_M69.4_M89.4 TS1M69.4 TS1M8
Microsoft Windows Server 20199.4_M69.4_M89.4 TS1M69.4 TS1M8
Windows 7 Enterprise 32 bit9.4_M69.4_M89.4 TS1M69.4 TS1M8
Windows 7 Enterprise x649.4_M69.4_M89.4 TS1M69.4 TS1M8
Windows 7 Home Premium 32 bit9.4_M69.4_M89.4 TS1M69.4 TS1M8
Windows 7 Home Premium x649.4_M69.4_M89.4 TS1M69.4 TS1M8
Windows 7 Professional 32 bit9.4_M69.4_M89.4 TS1M69.4 TS1M8
Windows 7 Professional x649.4_M69.4_M89.4 TS1M69.4 TS1M8
Windows 7 Ultimate 32 bit9.4_M69.4_M89.4 TS1M69.4 TS1M8
Windows 7 Ultimate x649.4_M69.4_M89.4 TS1M69.4 TS1M8
64-bit Enabled AIX9.4_M69.4_M89.4 TS1M69.4 TS1M8
64-bit Enabled Solaris9.4_M69.4_M89.4 TS1M69.4 TS1M8
HP-UX IPF9.4_M69.4_M89.4 TS1M69.4 TS1M8
Linux for x649.4_M69.4_M89.4 TS1M69.4 TS1M8
Solaris for x649.4_M69.4_M89.4 TS1M69.4 TS1M8
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.